I encountered this problem as well.
It does not affect iOS 16, but does affect iOS 17 and 18. It's reproducible in the simulator as well as on device.
In my case I was able to use DataRepresentation with a suggestedFileName instead.
In this example, it would look like this:
struct TextFile: Transferable {
let content: String
let filename: String
static var transferRepresentation: some TransferRepresentation {
DataRepresentation(exportedContentType: .data) {
textFile in
return textFile.content.data(using: .utf8) ?? Data()
}
.suggestedFileName {
textFile in
return textFile.filename
}
}
}
Caveats:
Requires iOS 17+ if you want to use this suggestedFileName method.
Isn't feasible for large files that won't fit in memory.
Alex at Astrocode
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution